home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group01b.txt
/
000005_icon-group-sender _Fri Jul 21 17:20:44 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2002-01-03
|
1KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.9.1a/8.9.1) id RAA11557
for icon-group-addresses; Fri, 21 Jul 2000 17:20:16 -0700 (MST)
Message-Id: <200007220020.RAA11557@baskerville.CS.Arizona.EDU>
To: "Charles Hethcoat" <CHETHCOA@oss.oceaneering.com>
Cc: icon-group@optima.CS.Arizona.EDU, unicon-group@cs.unlv.edu
Subject: Re: Unicon for NT
Date: Fri, 21 Jul 2000 16:09:27 -0700
From: Clinton L Jeffery <jeffery@bo.Egr.UNLV.EDU>
Errors-To: icon-group-errors@optima.CS.Arizona.EDU
Status: RO
Content-Length: 746
Charles Hethcoat recently asked whether Unicon for NT requires Microsoft's
commercial nmake program, and whether Unicon for NT is somehow less "free"
than Icon for NT or Unicon for Unix.
The answer is: the *source* distribution you downloaded at the moment has
only one NT configuration, which is for Visual C++. A binary distribution
for NT is in preparation, so yes Charles, the situation is temporary. Also,
I would love to see (and will assist anyone who wants to work on) new NT
configurations for other C compilers, especially free and semi-free C
compilers (e.g. gcc, lcc).
Cheers,
Clint
And now my mantra :-): if its about Unicon, route the discussion to
unicon-group@cs.unlv.edu; if its about Icon more generally, use icon-group.